Method and system for transferring an application program from system firmware to a storage device

ABSTRACT

One aspect of the invention is a method and system for accessing at least one storage element in a processor-based system. The system comprises a memory for storing instruction sequences by which the processor-based system is processed. The memory has at least one storage element. A processor is coupled to the memory, and a storage device is coupled to the processor. Prior to booting an operating system on the processor-based system, the stored instruction sequences cause the processor to write the contents of the at least one storage element to the storage device. Another aspect of the invention relates to a computer system having a user computer in communication with a remote service computer. The remote service computer has access to a database identifying information available to the service computer. A computer implemented method for transferring information to the user computer, comprises: writing the contents of at least one storage element to a storage device on the user computer prior to booting an operating system on the user computer, establishing a communications link between the user computer and the service computer, and presenting at the user computer, information available to the user computer.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to memory in processor-based ormicro-controller-based systems, and more particularly, to a system andmethod transferring an application program from system firmware to astorage device without the need for an operating system and/or adirectory service.

2. Description of the Related Art

In processor-based systems such as computers, an operating system mustfirst be installed before other application software may be subsequentlyinstalled and executed. The operating system software is typicallyinstalled from compact disks or diskettes. In certain cases, theoperating system must be extended via device drivers, or some othersoftware component, to bring the system up to a level of performancerequired by the motherboard manufacturer or the system manufacturer.This creates several problems, involving the transport of these devicedrivers.

Systems are manufactured in stages. The first stage involves thegathering of various components to construct a system motherboard. Thesecond stage involves creating a basic computer by combining a systemmotherboard with a power supply, hard drive and other internalcomponents. The third stage involves the integration of the basiccomputer with various peripherals such as a monitor, printer, speakers,keyboard, and mouse.

Each manufacturing stage may have unique requirements, advancements intechnology or involve different testing and failure resolutions. Becausethe various stages of manufacture can happen in different physicallocations, and in different companies, device drivers or specialsoftware that is added to the target operating system adds extra cost tothe system. This extra cost is incurred because the additional driversor special software must be transported on a floppy disk, a compactdisk, or other media with each system. Further, extra items like floppydisks or compact disks can easily be lost or stolen.

Moreover, as technology evolves, the system hardware can providefunctionality that current operating systems are unable to use. Today,there is no reliable method available for the system firmware or BIOS topass on the capability to control new hardware or provide extendedsystem functionality. For example, systems are now incorporatingreal-time video display. Although the hardware is present to do thisfunction, the operating system is unable to display the real-time video.As discussed earlier, a system manufacturer could supply the user with adiskette or compact disk (CD) that has the software necessary fordisplaying real-time video. The problem with this is that a motherboardcan pass through several middle men before it is incorporated into asystem and sold to and end-user, allowing the diskette or CD to beeasily lost or destroyed.

Accordingly, there is a need in the technology for a system and methodfor overcoming the aforementioned problems. In particular, there is aneed for a system and method for delivering applications from systemfirmware to a storage device without the need for or availability of anoperating system and/or a directory service.

BRIEF SUMMARY OF THE INVENTION

One aspect of the invention is a method and system for accessing atleast one storage element in a processor-based system. The systemcomprises a memory for storing instruction sequences by which theprocessor-based system is processed. The memory has at least one storageelement. A processor is coupled to the memory, and a storage device iscoupled to the processor. Prior to booting an operating system on theprocessor-based system, the stored instruction sequences cause theprocessor to write the contents of the at least one storage element tothe storage device.

Another aspect of the invention relates to a computer system having auser computer in communication with a remote service computer. Theremote service computer has access to a database identifying informationavailable to the service computer. A computer implemented method fortransferring information to the user computer, comprises: writing thecontents of at least one storage element to a storage device on the usercomputer prior to booting an operating system on the user computer,establishing a communications link between the user computer and theservice computer, and presenting at the user computer, informationavailable to the user computer.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system block diagram of one embodiment of an informationdistribution system in which the apparatus and method of the inventionis used.

FIG. 2A illustrates an exemplary processor system or user computersystem which implements embodiments of the present invention.

FIG. 2B depicts one embodiment of a sector allocation techniqueimplemented by typical operating systems for the first couple of headson cylinder number 0.

FIG. 3 illustrates a diagram of one embodiment of the computer system ofFIG. 2A, in which the apparatus and method of invention is used.

FIGS. 4A and 4B illustrate one embodiment of a system process flow chartprovided in accordance with the principles of the invention.

FIG. 5A illustrates a flowchart of one embodiment of the file or payloaddelivery process of the present invention.

FIG. 5B illustrates a flowchart of a second embodiment of the file orpayload delivery process 200B of the present invention.

FIGS. 6A and 6B illustrate a flow chart of one embodiment of the file orpayload application installation process 220 of FIG. 5A or 260 of FIG.5B.

FIGS. 7A and 7B are flowcharts illustrating one embodiment of the fileor payload installation process 360 of FIGS. 6A and 6B.

FIG. 8 is a flow chart of one embodiment of the transfer file or payloadprocess 465 or 485 of FIG. 7.

DETAILED DESCRIPTION OF THE PREFERRED INVENTION

The present invention relates to a system and method for providing anapplication without the need for an operating system or directoryservice. In one embodiment, the payload or file is initially stored in aprocessor system's non-volatile storage. A payload delivery programtransfers the file or payload into an initialization or start-updirectory of the system prior to installation of the file or payload.The file or payload is subsequently installed after the operating systemis fully booted.

The invention allows motherboard vendors to differentiate their productsby providing extended functionality that can be automatically installedwhen the operating system is updated or changed. This extendedfunctionality can operate new or “different” system hardware, or it canbe a software based capability, such as a branded Internet browser. Someoperating systems may be configured to automatically run a programduring the operating system boot if the program is placed in a specificdirectory.

Another aspect of the invention relates to a system and method forproviding an Infomediary. It involves the construction and maintenanceof a secure and private repository of Internet user and system profiles,collected primarily from warranty service registrations, internetservice registrations, system profiles and user preferences. Initially,this information is used to register the user with the manufacturers ofpurchased hardware and software products, and with the providers ofon-line or other services. Over time, the user data will be used toprofile and notify users of relevant software updates and upgrades, toencourage on-line purchases of related products and to enable one-to-onemarketing and other services.

A further aspect of the invention relates to pre-boot screen messaging.Software or firmware may be used to provide customized screens in theform of messages possibly with embedded graphics, during the pre-bootprocess of the system. These messages may take the form of anadvertisement. In one embodiment, graphics that was previously stored onROM may be retrieved for display on the screen during the pre-bootprocess. When a link has been established with the predetermined website, additional graphics may be used. Such additions include updates ormessages that are either provided arbitrarily or provided based on theinformation obtained from a survey of the user or the user's system. Inone embodiment, once the boot process is completed, a portion of thedisplay screen may be used to provide icons that are used to accessdetailed information regarding the previously displayed messages oradvertisements. In a further embodiment, the messages or advertisementsmay again be displayed during the shut-down process, for example,replacing the screen display that displays the message “Windows isshutting down” or “It is now safe to turn off your computer” with otherselected messages or advertisements.

Definitions

As discussed herein, a “computer system” is a product includingcircuitry capable of processing data. The computer system may include,but is not limited to, general purpose computer systems (e.g., server,laptop, desktop, palmtop, personal electronic devices, etc.), personalcomputers (PCs), hard copy equipment (e.g., printer, plotter, faxmachine, etc.), banking equipment (e.g., an automated teller machine),and the like. An infomediary is a web site that provides information onbehalf of producers of goods and services, supplying relevantinformation to businesses about products and/or services offered bysuppliers and other businesses. Content refers to application programs,driver programs, utility programs, file, payload, etc., and combinationsthereof, as well as graphics, informational material (articles, stockquotes, etc.) and the like, either singly or in any combination.“Payload” refers to messages with graphics or informational material(such as articles, stock quotes, etc.) and may include files orapplications. In one embodiment, it is transferred at a predeterminedtime to the system's mass storage media. In addition, a “communicationlink” refers to the medium or channel of communication. Thecommunication link may include, but is not limited to, a telephone line,a modem connection, an Internet connection, an Integrated ServicesDigital Network (“ISDN”) connection, an Asynchronous Transfer Mode (ATM)connection, a frame relay connection, an Ethernet connection, a coaxialconnection, a fiber optic connection, satellite connections (e.g.Digital Satellite Services, etc.), wireless connections, radio frequency(RF) links, electromagnetic links, two way paging connections, etc., andcombinations thereof.

In addition, the loading of an operating system (“OS”) refers to theinitial placement of the operating system bootstrap loader. In oneembodiment, during the OS load, a sector of information is typicallyloaded from a hard disk into the system memory. Alternatively, thebootstrap loader is loaded from a network into system memory. An OS“boot” refers to the execution of the bootstrap loader. This places theOS in control of the system. Some of the actions performed during the OSboot include system configuration, device detection, loading of driversand user logins. OS runtime refers to the completion of the boot phaseand the beginning of the execution of applications by the OS. In oneembodiment, during OS runtime, the OS interacts with the user to executeand/or run applications. Power On Self Test (“POST”) refers to theinstructions that are executed to configure and test the system hardwareprior to loading an OS.

System Overview

A description of an exemplary system, which incorporates embodiments ofthe present invention, is hereinafter described.

FIG. 1 shows a system block diagram of one embodiment of an informationdistribution system 10 in which the apparatus and method of theinvention is used. The system 10 relates to providing an infomediary. Itinvolves the construction and maintenance of a secure and privaterepository of Internet user and system profiles, collected primarilyfrom warranty service registrations, Internet service registrations,system profiles, and user preferences. Initially, this information isused to register the user with the manufacturers of purchased hardwareand software products, and with the providers of on-line or otherservices. Over time, the user data is used to create a user profile andnotify users of relevant software updates and upgrades, to encourageon-line purchases of related products, and to enable one-to-onecustomized marketing and other services.

In one embodiment, two software modules are used to implement variousembodiments of the invention. One is resident on a user's system, and isused to access a predetermined web site. For example, in one embodiment,the operating system and Basic Input and Output System (BIOS) arepre-installed on a computer system, and when the computer system issubsequently first powered up, an application, referred to fordiscussion purposes as the first software module (in one embodiment, thefirst software module is the initial start-up application (ISUA), whichwill be described in the following sections), will allow the launchingof one or more executable programs in the preboot environment. In oneembodiment, the first software module facilitates the launching of oneor more executable programs prior to the loading, booting, executionand/or running of the OS. In one embodiment, the user is encouraged toselect the use of such a program (i.e., the use of the first softwaremodule), and in alternative embodiments, the program is automaticallylaunched. The program(s) contained in the first software module enablestools and utilities to run at an appropriate time, and with proper userauthorization, also allow the user to download a second software modulethat includes drivers, applications and additional files or payloadsthrough the Internet connection on the PC. The programs may also providefor remote management of the system if the OS fails to launchsuccessfully.

Once the second software module has been delivered, it may become memoryresident, and may disable the transferred copy of the first softwaremodule. The original copy of the first software module still residing inthe system's non-volatile memory remains idle until the second softwaremodule fails to function, becomes corrupted or is deleted, upon which acopy of the original first software module is again transferred asdescribed above. The second software module may include an applicationthat connects the user to a specific server on the Internet and directsthe user to a predetermined web site to seek authorization to down loadfurther subscription material. The second software module may alsoinclude content that is the same or similar to the content of the firstsoftware module.

In one embodiment, the system may also include an initial payload thatis stored in Read Only Memory BIOS (ROM BIOS). In one embodiment, theinitial payload is part of the first software module (e.g., the ISUA).In an alternative embodiment, the initial payload is stored as a modulein ROM BIOS, separate from the first software module. In one embodiment,the initial payload is launched from ROM BIOS and displayed on thescreen after the Power On Self Test (POST) but prior to the booting,loading and/or execution of the OS. This may occur at a predeterminedtime, such as when the system is being manufactured, assembled andtested, or when the end user first activates the system. In an alternateembodiment, this initial payload is copied to a predetermined location(such as the system's hard disk) at a predetermined time, such as whenthe system is being manufactured, assembled and tested, or when the enduser first activates the system. Once copied, the payload executes afterPOST but prior to operation of the OS, and may display graphics,advertisements, animation, Joint Photographic Experts Group(JPEG)/Moving Picture Experts Group (MPEG) formatted material on thescreen. When additional programs and/or payloads are delivered (via theInternet or other outside connection), the display screen may be used toprovide customized screens in the form of messages or graphics prior toand during booting of the OS. In addition, executable programs deliveredin the first software module, as well as subsequent programs (such asthe second software module) downloaded from the web site, may be used tosurvey the PC to determine various types of devices, drivers, andapplications installed. In one embodiment, as described in co-pendingU.S. patent application Ser. No. 07/336,289, entitled “Method andApparatus for Automatically Installing And Configuring Software on aComputer” incorporated herein by reference, the first software module isused to identify and to automatically create shortcuts and/or bookmarksfor the user. The programs downloaded from the website may includesoftware that collects and maintains a user profile based on the user'spreferences. Such information may be provided to the infomediary, whichsubsequently forwards portions of the information and/or compiled databased on the information to suppliers and other businesses to obtainupdates or revisions of information provided by the suppliers and otherbusinesses.

Referring to FIG. 1, the information distribution system 10 comprises aservice center 20 that is connected over one or more communicationslinks 30 ₁-30 _(N) to one or more user computer systems 40 ₁-40 _(N)(“40”). The service center 20 includes one or more servers 22, one ormore databases 24, and one or more computers 26 ₁-26 _(M). The one ormore computers 26 ₁-26 _(M) are capable of simultaneous access by aplurality of the user computer systems 40 ₁-40 _(N). If a plurality ofcomputers are used, then the computers 26 ₁-26 _(M) may be connected bya local area network (LAN) or any other similar connection technology.However, it is also possible for the service center 20 to have otherconfigurations. For example, a smaller number of larger computers (i.e.a few mainframe, mini, etc. computers) with a number of internalprograms or processes running on the larger computers capable ofestablishing communications links to the user computers.

The service center 20 may also be connected to a remote network 50(e.g., the Internet) or a remote site (e.g., a satellite, which is notshown in FIG. 1). The remote network 50 or remote site allows theservice center 20 to provide a wider variety of computer software,content, etc. that could be stored at the service center 20. The one ormore databases 24 connected to the service center computer(s), e.g.,computer 26 ₁, are used to store database entries consisting of computersoftware available on the computer(s) 26. In one embodiment, each usercomputer 40 ₁-40 _(N) has its own secure database (not shown) that isnot accessible by any other computer. The communication links 30 ₁-30_(N) allow the one or more user computer systems 40 ₁-40 _(N) tosimultaneously connect to the computer(s) 26 ₁-26 _(M). The connectionsare managed by the server 22.

After a user computer system 40 establishes two-way communications withthe information service computer 26, the content is sent to the usercomputer system 40 in a manner hereinafter described. The downloadedcontent includes an application that surveys the user and/or the usercomputer system's hardware and/or software to develop a user profile aswell as a profile of the user's system. The information gathered fromthe user and/or user's computer system is subsequently provided to theservice center 20, which provides additional content to the usercomputer 40 based on the user and system profile. In one embodiment,such a transfer of user and system profile is provided in a securemanner, as described in co-pending U.S. patent application Ser. No.07/336,068, entitled “Method and apparatus for Transferring Profile Datato a Server Using a ROM-Based Security key,” filed Jun. 18, 1999,assigned to Phoenix Technologies Ltd., the contents of which areincorporated herein by reference. The database entries from the databaseconnected to the service computer 26 contain information about computersoftware, hardware, and third party services and products that areavailable to a user. Based on the user and/or system profile, thecontent is further sent to the user computer for display. The contentmay also include a summary of information such as the availability ofpatches and fixes for existing computer software, new versions ofexisting computer software, brand new computer software, new help files,etc. The content may further include information regarding availabilityof hardware and third party products and services that is of interest tothe user. The user is then able to make one or more choices from thesummary of available products and services, and request that theproducts be transferred from the service computer 26 to the usercomputer. Alternatively, the user may purchase the desired product orservice from the summary of available products and services.

FIG. 2A illustrates an exemplary computer system 100 that implementsembodiments of the present invention. The computer system 100illustrates one embodiment of user computer systems 40 ₁-40 _(N) and/orcomputers 26 ₁-26 _(M) (FIG. 1), although other embodiments may bereadily used.

Referring to FIG. 2A, the computer system 100 comprises a processor or acentral processing unit (CPU) 104. The illustrated CPU 104 includes anArithmetic Logic Unit (ALU) for performing computations, a collection ofregisters for temporary storage of data and instructions, and a controlunit for controlling operation for the system 100. In one embodiment,the CPU 104 includes any one of the x86, Pentium™, Pentium II™, andPentium Pro™ microprocessors as marketed by Intel™ Corporation, the K-6microprocessor as marketed by AMD™, or the 6x86MX microprocessor asmarketed by Cyrix™ Corp. Further examples include the Alpha™ processoras marketed by Digital Equipment Corporation™, the 680X0 processor asmarketed by Motorola™; or the Power PC™ processor as marketed by IBM™.In addition, any of a variety of other processors, including those fromSun Microsystems, MIPS, IBM, Motorola, NEC, Cyrix, AMD, Nexgen andothers may be used for implementing CPU 104. The CPU 104 is not limitedto microprocessor but may take on other forms such as microcontrollers,digital signal processors, reduced instruction set computers (RISC),application specific integrated circuits, and the like. Although shownwith one CPU 104, computer system 100 may alternatively include multipleprocessing units.

The CPU 104 is coupled to a bus controller 112 by way of a CPU bus 108.The bus controller 112 includes a memory controller 116 integratedtherein, though the memory controller 116 may be external to the buscontroller 112. The memory controller 116 provides an interface foraccess by the CPU 104 or other devices to system memory 124 via memorybus 120. In one embodiment, the system memory 124 includes synchronousdynamic random access memory (SDRAM). System memory 124 may optionallyinclude any additional or alternative high speed memory device or memorycircuitry. The bus controller 112 is coupled to a system bus 128 thatmay be a peripheral component interconnect (PCI) bus, Industry StandardArchitecture (ISA) bus, etc. Coupled to the system bus 128 are agraphics controller, a graphics engine or a video controller 132, a massstorage device 152, a communication interface device 156, one or moreinput/output (I/O) devices 168 ₁-168 _(N), and an expansion buscontroller 172. The video controller 132 is coupled to a video memory136 (e.g., 8 Megabytes) and video BIOS 140, all of which may beintegrated onto a single card or device, as designated by numeral 144.The video memory 136 is used to contain display data for displayinginformation on the display screen 148, and the video BIOS 140 includescode and video services for controlling the video controller 132. Inanother embodiment, the video controller 132 is coupled to the CPU 104through an Advanced Graphics Port (AGP) bus.

The mass storage device 152 includes (but is not limited to) a harddisk, floppy disk, CD-ROM, DVD-ROM, tape, high density floppy, highcapacity removable media, low capacity removable media, solid statememory device, etc., and combinations thereof. The mass storage device152 may include any other mass storage medium. The communicationinterface device 156 includes a network card, a modem interface, etc.for accessing network 164 via communications link 160. The I/O devices168 ₁-168 _(N) include a keyboard, mouse, audio/sound card, printer, andthe like. The I/O devices 168 ₁-168 _(n), may be disk drive, such as acompact disk drive, a digital disk drive, a tape drive, a zip drive, ajazz drive, a digital video disk (DVD) drive, a magneto-optical diskdrive, a high density floppy drive, a high capacity removable mediadrive, a low capacity media device, and/or any combination thereof. Theexpansion bus controller 172 is coupled to non-volatile memory 175,which includes system firmware 176. The system firmware 176 includessystem BIOS 82, which is for controlling, among other things, hardwaredevices in the computer system 100. The system firmware 176 alsoincludes ROM 180 and flash (or EEPROM) 184. The expansion bus controller172 is also coupled to expansion memory 188 a having RAM, ROM, and/orflash memory (not shown). The system 100 may additionally include amemory module 190 that is coupled to the bus controller 112. In oneembodiment, the memory module 190 comprises a ROM 192 and flash (orEEPROM) 194.

As is familiar to those skilled in the art, the computer system 100further includes an operating system (OS) and at least one applicationprogram, which in one embodiment, are loaded into system memory 124 frommass storage device 152 and launched after POST. The OS may include anytype of OS including, but not limited or restricted to, DOS, Windows™(e.g., Windows 95™, Windows 98™, Windows NT™), Unix, Linux, OS/2, OS/9,Xenix, etc. The operating system is a set of one or more programs whichcontrol the computer system's operation and the allocation of resources.The application program is a set of one or more software programs thatperforms a task desired by the user.

In accordance with the practices of persons skilled in the art ofcomputer programming, the present invention is described below withreference to symbolic representations of operations that are performedby computer system 100, unless indicated otherwise. Such operations aresometimes referred to as being computer-executed. It will be appreciatedthat operations that are symbolically represented include themanipulation by CPU 104 of electrical signals representing data bits andthe maintenance of data bits at memory locations in system memory 124,as well as other processing of signals. The memory locations where databits are maintained are physical locations that have particularelectrical, magnetic, optical, or organic properties corresponding tothe data bits.

When implemented in software, the elements of the present invention areessentially the code segments to perform the necessary tasks. Theprogram or code segments can be stored in a processor readable medium ortransmitted by a computer data signal embodied in a carrier wave over atransmission medium or communication link. The “processor readablemedium” may include any medium that can store or transfer information.Examples of the processor readable medium include an electronic circuit,a semiconductor memory device, a ROM, a flash memory, an erasable ROM(EROM), a floppy diskette, a CD-ROM, an optical disk, a hard disk, afiber optic medium, a radio frequency (RF) link, etc. The computer datasignal may include any signal that can propagate over a transmissionmedium such as electronic network channels, optical fibers, air,electromagnetic, RF links, etc. The code segments may be downloaded viacomputer networks such as the Internet, Intranet, etc.

The computer's operating system typically specifies a particularorganization of data on a hard disk. To facilitate the storage andretrieval of data in an orderly manner, computer hard disks aretypically organized in blocks called sectors. These sectors are locatedon the disk by a set of unique specifiers called cylinder (or track),head (or side) and sector number. In personal computers, cylinders areconventionally numbered from zero to the maximum allowed by a givendisk; heads are numbered from zero to the maximum number for a givencylinder and sectors are numbered from 1 to the highest sector numberfor a given cylinder and head. Alternatively, these unique identifiersmay simply be a sector number that stands at O-NN, where NN is thehighest sector number.

FIG. 2B depicts one embodiment of a sector allocation techniqueimplemented by typical operating systems for the first couple of headson cylinder number 0. The BIOS supports a hard disk that includes aconvention of reading the cylinder 0, head 0, sector 1 from the firsthard disk to boot the operating system. This sector (0/0/1) is known asthe Master Boot Record or partition sector, and contains informationregarding how the hard disk is divided into partitions and providesenough executable code to locate the partition that is marked asbootable. The partition sector includes information regarding theindividual partitions and is stored using partition entries in apartition table. During the boot process, the first sector of thepartition is copied to memory and then executed.

FIG. 3 illustrates a logical diagram of computer system 100. Referringto FIGS. 2A and 3, the system firmware 176 includes software modules anddata that are loaded into system memory 124 during POST and subsequentlyexecuted by the processor 104. In one embodiment, the system firmware176 includes a system BIOS module 82 having system BIOS handlers,hardware routines, etc., a ROM application program interface (RAPI)module 84, an initial start-up application (ISUA) module 86, an initialpayload 88 a, cryptographic keys 90, a cryptographic engine 92, and adisplay engine 94. RAPI 84 provides a secure interface between ROMapplication programs and system BIOS 82. The aforementioned modules andportions of system firmware 176 may be contained in ROM 180 and/or flash184. Alternatively, the aforementioned modules and portions of systemfirmware 176 may be contained in ROM 190 and/or flash 194. The RAPI 84,ISUA 86, and initial payload 88 a may each be separately developed andstored in the system firmware 176 prior to initial use of the computersystem 100. In one embodiment, the RAPI 84, ISUA 86, and initial payload88 a each includes proprietary software developed by PhoenixTechnologies, Ltd. One embodiment of RAPI 84 is described in co-pendingU.S. patent application Ser. No. 09/336,889, entitled “System and Methodfor Securely Utilizing Basic Input and Output System (BIOS) Services,”filed on Jun. 18, 1999, assigned to Phoenix Technologies, Ltd., andwhich is incorporated herein by reference. One embodiment of ISUA 86 isdescribed in co-pending U.S. patent application Ser. No. 09/336,289,entitled “Method and Apparatus for Automatically Installing andConfiguring Software on a Computer,” filed on Jun. 18, 1999, assigned toPhoenix Technologies, Ltd., the contents of which are incorporatedherein by reference.

In one embodiment, as shown in FIGS. 3 and 4A and 4B, after power isinitially turned on to a new computer system 100, the system commenceswith POST procedures. During the initial POST, the ISUA 86 istransferred to the mass storage device 152, as shown by A1. In oneembodiment, such a transfer is made during the manufacturing and/orassembly process, when the system 100 is first powered up after theoperating system has been installed (but prior to booting, loading andrunning of the operating system). In an alternative embodiment, such atransfer may be made after the manufacturing and/or assembly process,after the user receives and powers up the system 100. In a furtheralternate embodiment, during the transfer of the ISUA 86, additionalprograms, applications, drivers, data, graphics and other informationmay also be transferred (for example, from ROM) to the mass storagedevice 152. For example, the transfer may include the transfer of theinitial payload 88 a to the mass storage device 152, subsequent to whichthe initial payload is delivered from the mass storage device 152.Alternatively, the initial payload may be delivered from the ROM. Oneembodiment of the transfer process is described in FIGS. 5-8 and in theaccompanying text (see “Delivery Process”). Alternative embodiments ofthe system and process for facilitating such a transfer are described inco-pending U.S. patent application Ser. No. 09/272,859, entitled “Methodand Apparatus for Providing Memory-based Device Emulation” filed on Mar.19, 1999, in co-pending U.S. patent Continuation-in-Part applicationSer. No. 09/336,307, entitled “Method and Apparatus for ProvidingMemory-Based Device Emulation” filed on Jun. 18, 1999, and in co-pendingU.S. patent application Ser. No. 09/336,281, entitled “System and Methodfor Inserting One or More Files Onto Mass Storage” filed Jun. 18, 1999,each of which is assigned to Phoenix Technologies, Ltd., the assignee ofthe present invention, the contents of each of which are incorporatedherein by reference. In one further embodiment, if, after the transferof the ISUA 86, it is found that ISUA 85 is not functioning or isdefective, it is automatically de-installed. One technique for suchde-installation is described in co-pending U.S. patent application Ser.No. 09/336,254, entitled “Method and Apparatus to AutomaticallyDe-Install an Application Module When Not Functioning,” filed Jun. 18,1999, assigned to Phoenix Technologies Ltd., the assignee of the presentinvention, the contents of which are incorporated herein by reference.

In one embodiment, the ISUA 86 is a computer software executable programthat will determine if there are preinstalled programs that are residenton the end user's system. If so, it will identify those preinstalledprograms and create shortcuts (on the desktop in the case of a Windowsoperating system), or bookmarks, to allow the user to automaticallylaunch the programs. In this embodiment, the executable program is alsocapable of initiating and establishing two-way communications with oneor more applications on the server 22 and/or any one of the servicecomputers 26 (FIG. 1), as described below. Moreover, in one embodiment,graphical content of the initial payload 88 a is displayed by displayengine 94 on the user's display screen 148 during POST. Alternatively,the graphical content of the initial payload 88 a may be displayed aftera subsequent booting process. For example, as part of the user's profileas described below, the user may be asked if he or she would like toobtain additional information regarding one or more products and/orservices. If the user so desires, content regarding the desired productsand/or services will be displayed during subsequent boot processes. Inone embodiment, such a display process is described in co-pending U.S.patent application Ser. No. 09/336,180, entitled “Method and Apparatusfor Extending BIOS Control of Screen Display Beyond Operating SystemBoot,” assigned to Phoenix Technologies Ltd., the assignee of thepresent invention, the contents of which are incorporated herein byreference.

Once POST is completed, the OS is loaded, executed, and initialized.Standard OS drivers and services are then loaded. The user is thenprompted to enter registration information including demographicinformation such as age, gender, hobbies, etc. In addition, the ISUA 86is executed, and runs in the background, remaining idle until it detectsa communication link established between the computer system 100 and aremote server (e.g., server 22 of FIG. 1) over Network 164 of FIG. 2A(e.g., over the Internet). It should be noted that although ISUA 86 isshown as being stored in system firmware 176, it may alternatively belocated in system memory 124, memory module 190, mass storage 152, anyof the I/O devices 168 or provided in a communication interface 156.

In one embodiment, the ISUA 86 may search through the operating systemto determine if there are applications that have been pre-loaded andpre-installed onto the system. If so, the ISUA 86 may automaticallyprovide short cuts and/or bookmarks for the applications to launch intoa predetermined server once the communication link is established. Thiscommunication link can be established with a network protocol stack,(e.g. TCP/IP) through sockets, or any other two-way communicationstechnique known in the art. Once the communication link 30 isestablished, the ISUA 86 issues a request signal to the server 22 (asshown by A2) to download an initial content package 62 from a contentmodule 60. Responsive to the request, the server downloads the initialcontent package 62 (as shown by A3), which, in one embodiment, is storedin the mass storage device 152. In one embodiment, the initial content62 and subsequent content 64 may be developed separately, and each isencrypted and/or digitally signed using encryption keys, prior tostoring of the initial content 62 and subsequent content 64 on theserver 22. When the initial content 62 and/or subsequent content 64is/are subsequently downloaded into system 100, the crypto engine 92will use keys 90 to decrypt the initial content 62 and/or subsequentcontent 64.

As discussed earlier, the initial content package 62 may includeapplications 62 a, drivers 62 b, and payloads 62 c. In one embodiment,the applications 62 a include a data loader application and a profilemanager application. The data loader application functions in the sameor a similar manner as ISUA 86, and once downloaded, disables andreplaces the ISUA 86. More specifically, the data loader application isa computer software program which is also capable of initiating,establishing, and terminating two-way communications between the server22 and the computer system 100. The data loader application alsoprovides traffic control management between the server 22 and computersystem 100, as well as other functions to facilitate communicationbetween the end user's system and the designated server, and contentdownloading to the end user's system.

The profile manager obtains the user and system profiles of the computersystem 100 based on user preferences, system hardware, and softwareinstalled at the computer system 100. Upon obtaining the user and systemprofile of the computer system 100, the profile manager applicationforwards the results to the data loader application, which subsequentlyprovides the information to the server 22, which matches the userindicted preferences with database 24 (FIG. 1). The results may beforwarded at predetermined intervals or at the user's request. Theserver 22 then processes the user profile or demographic data andtargets content to the users which have similar profiles. In addition,the user profile data of a plurality of users are compiled on the server22 and aggregated to create an aggregate user profile model. Content isthen transmitted to user computer system's based on the user profiledata and/or the aggregate user profile model (as shown by A4). Thesubsequent content 64 is downloaded and stored in system firmware 176,designated by numeral 88 b. In one embodiment, the subsequent content 64is stored in non-volatile memory such as flash or EEPROM, with theloading of the subsequent content being done by reflashing the ROM, asis well known by those skilled in the art. The subsequent content 64 mayalso be stored as one or more files on mass storage device 152 or may beused to modify the Windows™ system file (under the Windows™environment). The profile collection process is continued as long as thecomputer system 100 is activated. In one embodiment, content may bedownloaded after the user's profile is received and analyzed at theserver 22.

When the computer system 100 is subsequently powered up (see FIG. 4B),the system again performs POST. The content that was previouslydownloaded and stored in system firmware 176, and subject to copyrightissues being resolved, is then displayed, prior to loading and/orexecution of the operating system or while the OS is loading. In oneembodiment, such a display process is described in co-pending U.S.patent application Ser. No. 09/336 180, entitled “Method and Apparatusfor Extending BIOS Control of Screen Display Beyond Operating SystemBoot,” filed Jun. 18, 1999, assigned to Phoenix Technologies Ltd., theassignee of the present invention, the contents of which areincorporated herein by reference. Such a process may be used to extendthe display content beyond the loading of the operating system. In theWindows™ environment, the Windows™ logo, which is displayed during theinitial loading of the operating system, is subsequently replaced by oneor more screen that display the previously downloaded content stored insystem firmware 176.

In the case of storing the content as one or more files on the massstorage device 152, as opposed to reflashing the ROM, the Windows™ logofile, which is displayed during boot-up and shutdown, may be altered orreplaced. One embodiment utilizing this approach involves replacing thecorresponding Windows™ system files with the one or more files showingthe content (e.g., a graphic file), as described in co-pending U.S.patent application Ser. No. 09/336,003, entitled “Displaying Imagesduring Boot-up and Shut-down” filed on Jun. 18, 1999, which is assignedto Phoenix Technologies, LTD., the contents of which are incorporatedherein by reference. The boot-up Windows display file is named LOGO.SYSand is usually located in the Windows directory. First the Windows™LOGO.SYS file is transferred from the Windows directory to anotherdirectory. Then, the content graphics file is renamed as LOGO.SYS and istransferred to the Windows™ directory. The operating system retrievesthis file when the operating system is first launched, and hence thecontent is displayed on the display screen. Windows™ expects theLOGO.SYS file to be a bit-mapped file with resolution 320×400 and 256colors although Windows™ will later stretch the resolution to 640×400for displaying purposes. Therefore, the content graphics file is to bethe same graphics format (usually named with the extension “.BMP” beforebeing renamed to LOGO.SYS).

The operating system is then loaded, executed, and initialized. Thestandard operating system drivers and applications are also loaded. Theprofile manager is then executed. When a link has been established withthe predetermined web site, additional content may be downloaded andsubsequently displayed. Such additional content are either providedarbitrarily or provided based on the information obtained from a surveyof the user or the user's system. In one embodiment, once the bootprocess is completed, a portion of the display screen may be used toprovide icons or shortcuts that are used to access detailed informationregarding the previously displayed messages or advertisements. In afurther embodiment, the messages or advertisements may again bedisplayed during the shut-down process, for example, replacing thescreen display that displays the message “Windows is shutting down” or“It is now safe to turn off your computer” with other selected content.

DELIVERY PROCESS

FIG. 5A illustrates a flowchart of one embodiment of the file or payloaddelivery process 200A of the present invention. In one embodiment, thefile or payload comprises at least one application program. In analternate embodiment, the file comprises data and/or graphics. The filemay also comprise a payload. The file or payload delivery process 200Ais an application (that may be stored in system memory 124, memory 176(see FIG. 2A), expansion memory 188 a, memory module 190 or be providedvia any of the peripheral modules 168 ₁-168 _(N)) that transfers apayload from a nonvolatile storage to a predetermined device. In oneembodiment, the predetermined device is a mass storage device 152, suchas a hard disk. In alternate embodiments, the device may be any storagedevice, including but not limited to a CD ROM, a zip disk, a floppy diskand flash memory.

Beginning from a power-on start state, the process 200A proceeds todecision block 210 where it queries if the previous boot process hadfailed. If so, the process 200A advances to process block 220, where itinstalls the file, application or payload. The process 200A thenproceeds to process block 230, where it proceeds with the normal bootprocess. If, at decision block 210, the process determined that theprevious boot process had failed, it advances to decision block 240,where it queries if the previous boot installation process wassuccessful. One example of an unsuccessful boot installation processincludes abortion of the boot process by the user. If the previous bootinstallation process was unsuccessful, the process proceeds to processblock 220, where the file or payload is installed. Otherwise, theprocess 200A is complete.

FIG. 5B illustrates a flowchart of a second embodiment of the file orpayload delivery process 200B of the present invention. Beginning from apower-on start state, the process 200B proceeds to decision block 250where it queries if the previous boot process had failed. If so, theprocess 200B advances to process block 260, where it installs the fileor payload. The process 200B then proceeds to process block 270, whereit proceeds with the normal boot process. If, at decision block 250, theprocess 200B determined that the previous boot process had failed, itadvances to decision block 280, where it queries if the previous bootinstallation process was successful. If so, the process 200B iscomplete. If not, the process proceeds to decision block 290, where itdetermines if installation of the file or payload should be disabled. Ifnot, the process 200B proceeds to process block 260, where the file orpayload is installed. Otherwise, the process 200B is complete.

FIGS. 6A and 6B illustrate a flow chart of one embodiment of the file orpayload application installation process 220 of FIG. 5A or 260 of FIG.5B. For discussion purposes, this process will be referred to as theprocess 220. Commencing from a start state, the process 220 advances toprocess block 300, where it locates the first device installed on thesystem. In one embodiment, the first device is a mass storage devicesuch as a hard disk. The process 220 next reads the first sector of thedisk (process block 305). In one embodiment, the first sector is a bootsector of the device. The process 220 then determines if there was anerror in reading the first sector (decision block 310). If so, theprocess 220 proceeds to process block 315, where it locates the nextdevice installed on the system. If, at decision block 310, there was noerror in reading the first sector, the process 220 proceeds to check forthe existence of a supported file system (process block 320). Theprocess 220 performs this by first determining if a partition table ispresent on the device, as shown in decision block 325. If not, itproceeds to process block 315, where it locates the next device.Otherwise, it proceeds to decision block 330, where it examines thepartition table to determine if the partition is active. If not, itproceeds to process block 315. Otherwise, it proceeds to decision block335.

At decision block 335, the process 220 queries if the file system on thedevice is a supported or known system. If not, the process 220 proceedsto process block 340, where it issues an error message, such as “filesystem is not supported” and exits. If the file system is supported orknown, the process 220 proceeds to process block 345, where it reads thefile system's directory structure and parses through the knownsubdirectories. The process 220 then determines the operating system byreading a set of specific files and parses the content of the files. Theprocess 220 then queries if there is an initialization or start-updirectory. A start-up directory is a directory that is used by defaultto locate files of information when it starts up. If so, the process 220proceeds to decision block 355, where it queries if there is a start-updirectory. If so, the process 220 installs the file or payload (processblock 360) and then terminates. Otherwise, the process 220 issues amessage or signal indicating that there is no start-up directory, asshown in process block 365, and exits.

FIG. 7 is a flowchart illustrating one embodiment of the file or payloadinstallation process 360 of FIGS. 6A and 6B. Commencing from a startstate, the process 360 proceeds to process block 400, where it locatesthe root directory of the file system. The process 360 then queries if asecondary directory, for example, a Windows directory, is available(process block 415). If so, the process 360 proceeds to process block420, where it advances to the secondary directory. The process 360 thenqueries if a tertiary directory (such as a profiles directory) isavailable (process block 425). If so, the process 360 proceeds toprocess block 430. Otherwise, it issues an error message (process block435) and exits. If, at decision block 425, the process 360 determinesthat the secondary directory is not available, it proceeds to processblock 440, where it searches all the subdirectories for the tertiarydirectory. The process 360 then moves on to decision block 445, where itqueries if the tertiary directory is found. If not, it proceeds toprocess block 435. Otherwise, it proceeds to process block 430, where itadvances to the tertiary directory.

The process 360 then locates the start-up directory, as shown in processblock 450. It subsequently determines if the start-up directory isfound, as shown in decision block 455. If not, it issues an errormessage (process block 460) and exits. Otherwise, it transfers the fileor payload to the start-up directory (process block 465). The process360 subsequently locates the next start-up directory (process block470). It queries if the next start-up directory is found (decision block475). If not, the process 360 is complete, and terminates. Otherwise, itproceeds to process block 485, where it transfers the file or payload tothe next start up directory and returns to process block 470 to locatethe next start-up directory.

FIG. 8 is a flow chart of one embodiment of the transfer file or payloadprocess 465 or 485 of FIG. 7. For present discussion purposes, theprocesses 465 and 485 will be referred to as process 465. Beginning froma start state, the process 465 proceeds to process block 500, where itattempts to locate a free (unoccupied) directory entry. The process 465next queries if the free directory entry is found (decision block 505).If so, it writes the name of the file or payload to the directory found(process block 510). Otherwise, it allocates a new directory page(process block 515) and advances to decision block 520, where itdetermines if the allocation is successful. If so, it proceeds toprocess block 510. Otherwise, it proceeds to process block 525, where itissues a failure message and exits.

From process block 510, the process 465 proceeds to process block 530,where it locates a free (unoccupied) space for transfer of the file orpayload. It subsequently queries if this space is available, as shown indecision block 535. If not, the process 465 proceeds to process block525. Otherwise, it proceeds to process block 540, where it transfers thefile or payload to the space found on the device. The process 465 thenadjusts the directory entry to point to the file or payload, andthereafter, terminates.

The present invention thus provides a system and method for deliveringapplications from system firmware to a storage device (such as compactdisk (CD) drive, digital disk drive (DVD) drive, tape drive, floppydrive, hard drive, magneto-optical drive, document scanner, solid statememory device, zip drive, jazz drive, high density floppy drive (such asthe Sony Hi FD drive), high capacity removable media device, lowcapacity removable media device, and combination high and low capacityremovable media device (such as the Panasonic LS 120/super disk drive))without the need for or availability of an operating system or adirectory service.

Although the present invention has been described in terms of certainpreferred embodiments, other embodiments apparent to those of ordinaryskill in the art are also within the scope of this invention.Accordingly, the scope of the invention is intended to be defined onlyby the claims which follow.

What is claimed is:
 1. A system for accessing at least one storageelement in a processor-based system, comprising: a memory for storinginstruction sequences by which the processor-based system is processed,the memory having at least one storage element; a processor coupled tosaid memory, the processor executes the stored instruction sequences;and a storage device coupled to the processor, where said storage deviceis local to the processor and the memory; wherein prior to booting anoperating system, the stored instruction sequences cause the processorto write the contents of the at least one storage element to the storagedevice, said act of writing being performed independent of a post-bootapplication program.
 2. The system of claim 1, wherein the act ofwriting the contents of the at least one storage element to the storagedevice occurs prior to loading the operating system.
 3. The system ofclaim 1, wherein the instruction sequences further cause the processorto initiate a boot sequence.
 4. The system of claim 1, wherein the atleast one storage element is a non-volatile memory.
 5. The system ofclaim 2, wherein the storage device is selected from a group consistingof: a compact disk drive, a digital video disk (DVD) drive, a solidstate memory device, a digital disk drive, a hard disk drive,magneto-optical disk drive, a tape drive, a zip drive, a jazz drive, ahigh density floppy drive, a high capacity removable media device, a lowcapacity removable media device, and a combination high and low capacityremovable media device.
 6. The system of claim 1, wherein the storagedevice comprises a file system; wherein in the act of writing thecontents of the at least one storage element to the storage device, theat least one storage element is a file; and wherein the act of writingcomprises transferring said file to said file system in said storagedevice.
 7. The system of claim 1, wherein writing the contents of the atleast one storage element to the storage device comprises: (a) locatinga start-up directory stored in said memory; (b) writing a namecorresponding to the at least one storage element, to said start-updirectory; and (c) transferring the contents of said at least onestorage element to said storage device; (d) setting a directory pointerto said transferred contents.
 8. A method for accessing at least onestorage element in a processor-based system having a processor coupledto the at least one storage element and a storage device coupled to theprocessor, said storage device being local to the processor, comprising:writing the contents of the at least one storage element to the storagedevice prior to booting an operating system on the processor-basedsystem, wherein said writing is performed independent of a post-bootapplication program.
 9. The method of claim 8, wherein the act ofwriting the contents of the at least one storage element to the storagedevice occurs prior to loading the operating system.
 10. The method ofclaim 8, further comprising initiating a boot sequence.
 11. The methodof claim 8, wherein in the act of writing, the at least one storageelement is a non-volatile memory.
 12. The method of claim 8, wherein thestorage device is selected from a group consisting of: a compact diskdrive, a digital disk drive, a digital video disk (DVD) drive, a solidstate memory device, a hard disk drive, magneto-optical disk drive, atape drive, a zip drive, a jazz drive, a high density floppy drive, ahigh capacity removable media device, a low capacity removable mediadevice, and a combination high and low capacity removable media device.13. The method of claim 8, wherein the storage device comprises a filesystem; wherein in the act of writing the contents of the at least onestorage element to the storage device, the at least one storage elementis a file; and wherein the act of writing comprises transferring saidfile to said file system in said storage device.
 14. The method of claim8, wherein writing the contents of the at least one storage element tothe storage device comprises: (a) locating a start-up directory storedin said memory; (b) writing a name corresponding to the at least onestorage element, to said start-up directory; (c) transferring thecontents of said at least one storage element to said storage device;(d) setting a directory pointer to said transferred contents.
 15. Acomputer readable program product, comprising: a computer usable mediumhaving computer program code embodied therein for accessing at least onestorage element in a processor-based system, the computer programproduct having: computer readable program code for writing the contentof the at least one storage element to a storage device prior to bootingan operating system on the processor-based system, said storage deviceto be local to the at least one storage element, said act of writingbeing performed independent of a post-boot application program.
 16. Thecomputer readable program product of claim 15, wherein the computerreadable program code writes the contents of the at least one storageelement to the storage device occurs prior to loading the operatingsystem.
 17. The computer readable program product of claim 15, furthercomprising computer readable program code for initiating a boot sequencesubsequent to the act of writing.
 18. The computer readable programproduct of claim 15, wherein the at least one storage element is anon-volatile memory.
 19. The computer readable program product of claim15, wherein the storage device is selected from a group consisting of: acompact disk drive, a digital disk drive, a digital video disk (DVD)drive, a solid state memory device, a hard disk drive, a magneto-opticaldisk drive, a tape drive, a zip drive, a jazz drive, a high densityfloppy drive, a high capacity removable media device, a low capacityremovable media device, and a combination high and low capacityremovable media device.
 20. The computer readable program product ofclaim 15, wherein the storage device comprises a file system; wherein inthe act of writing the contents of the at least one storage element tothe storage device, the at least one storage element is a file; andwherein the act of writing comprises transferring said file to said filesystem in said storage device.
 21. The computer program product of claim15, wherein the computer readable program code for writing the contentsof the at least one storage element to the storage device comprises: (a)computer readable program code for locating a start-up directory storedin said memory; (b) computer readable program code for writing a namecorresponding to the at least one storage element, to said start-updirectory; (c) computer readable program code for transferring thecontents of said at least one storage element to said storage device;(d) computer readable program code for setting a directory pointer tosaid transferred contents.
 22. In a computer system having a usercomputer in communication with a remote service computer having accessto a database identifying information available to the service computer,a computer implemented method for transferring information to the usercomputer, comprising: (a) writing the contents of at least one storageelement of the user computer to a storage device on the user computerprior to booting an operating system on the user computer, said writingbeing performed independent of a post-boot application program; (b)establishing a communications link between the user computer and theservice computer; and (c) presenting at the user computer, informationavailable to the user computer.
 23. The method of claim 22, wherein in(a), the contents of the at least one storage element comprises anapplication program, and wherein the method further comprises:initiating, by the application program, a transfer of software from theservice computer to the user computer, subsequent to (b); receiving, bythe user computer, said software, wherein the software comprises atleast one program that collects system information regarding the usercomputer.
 24. The method of claim 23, further comprising: providing thesystem information to the service computer; presenting, by servicecomputer, information based on the system information.